fix(spring-kafka-example): update to the latest version and fix bugs#25
fix(spring-kafka-example): update to the latest version and fix bugs#25igorcampos-dev merged 1 commit intomasterfrom
Conversation
WalkthroughThe Docker Compose configuration for the Spring Kafka example was updated to remove the Zookeeper service and transition the Kafka service to run in KRaft (Kafka Raft) mode. This involved deleting Zookeeper-related settings and introducing KRaft-specific environment variables and listener configurations. Changes
Estimated code review effort2 (~15 minutes) 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
There was a problem hiding this comment.
Actionable comments posted: 2
📜 Review details
Configuration used: CodeRabbit UI
Review profile: ASSERTIVE
Plan: Pro
📒 Files selected for processing (1)
spring-kafka-example/compose.yaml(1 hunks)
🧠 Learnings (1)
📓 Common learnings
Learnt from: igorcampos-dev
PR: igorcampos-dev/spring-integrations-examples#21
File: spring-kafka-example/README.md:12-17
Timestamp: 2025-07-22T01:35:41.364Z
Learning: User igorcampos-dev prefers minimal, high-level documentation in README files without detailed version specifications, choosing to keep tech stack information simple rather than adding precise version numbers.
Learnt from: igorcampos-dev
PR: igorcampos-dev/spring-integrations-examples#21
File: spring-kafka-example/compose.yaml:30-32
Timestamp: 2025-07-22T01:30:57.030Z
Learning: User igorcampos-dev prefers to maintain environment parity between local development and production, avoiding development-specific configurations like ALLOW_PLAINTEXT_LISTENER even when they might provide clearer intent or safety nets.
🪛 YAMLlint (1.37.1)
spring-kafka-example/compose.yaml
[error] 27-27: no new line character at the end of file
(new-line-at-end-of-file)
🧰 Additional context used
🧠 Learnings (1)
📓 Common learnings
Learnt from: igorcampos-dev
PR: igorcampos-dev/spring-integrations-examples#21
File: spring-kafka-example/README.md:12-17
Timestamp: 2025-07-22T01:35:41.364Z
Learning: User igorcampos-dev prefers minimal, high-level documentation in README files without detailed version specifications, choosing to keep tech stack information simple rather than adding precise version numbers.
Learnt from: igorcampos-dev
PR: igorcampos-dev/spring-integrations-examples#21
File: spring-kafka-example/compose.yaml:30-32
Timestamp: 2025-07-22T01:30:57.030Z
Learning: User igorcampos-dev prefers to maintain environment parity between local development and production, avoiding development-specific configurations like ALLOW_PLAINTEXT_LISTENER even when they might provide clearer intent or safety nets.
🪛 YAMLlint (1.37.1)
spring-kafka-example/compose.yaml
[error] 27-27: no new line character at the end of file
(new-line-at-end-of-file)
🔇 Additional comments (1)
spring-kafka-example/compose.yaml (1)
14-14: Hard-codingcontainer_namemay collide with other stacksGiving the service a fixed
container_name: kafkaprevents running multiple compose projects in parallel and breaks compose’s automatic hostname resolution (kafkais already reachable by service name). Consider removing it unless you have a compelling production need.
Summary by CodeRabbit